Techniques to manage service requests in a wireless network

ABSTRACT

Embodiments are directed to techniques to manage service requests in a wireless network. In one embodiment, an apparatus may comprise processing circuitry. The apparatus may further include computer-readable storage media having stored thereon instructions for execution by the processing circuitry. The instructions, when executed, may determine, at user equipment (UE) operating in an Evolved Packet System (EPS) mobility management (EMM)-IDLE mode and configured to use EPS services with control plane Cellular Internet of Things (CIoT) EPS optimization, to initiate a service request procedure to enable transfer of user data via a control plane, generate a service request message that contains a service type information element (IE) comprising a service type value set to indicate either a mobile originating request or a mobile terminating request, and send the service request message to a mobility management entity (MME) to initiate the service request procedure. Other embodiments are described and claimed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a national phase application claiming the benefit ofand priority to International Patent Application No. PCT/US2017/015876,entitled “TECHNIQUES TO MANAGE SERVICE REQUESTS IN A WIRELESS NETWORK”filed Jan. 31, 2017, which claims priority to U.S. Provisional PatentApplication No. 62/329,328, filed Apr. 29, 2016, both of which arehereby incorporated by reference in their entirety.

RELATED CASE

This application claims the benefit of priority under 35 U.S.C. § 119(e)to United States Provisional Patent Application No. 62/329,328, filedApr. 29, 2016, the entirety of which is hereby incorporated byreference.

TECHNICAL FIELD

Embodiments herein generally relate to communications between devices inwireless communications networks.

BACKGROUND

With a wide range of potential applications, machine type communication(MTC) or machine to machine (M2M) communication is gaining a tremendousinterest among mobile network operators, equipment vendors, MTCspecialist companies, and research bodies. The idea of M2Mcommunications is to enable M2M components to be interconnected,networked, and controlled remotely with low-cost scalable and reliabletechnologies. M2M communication could be carried over mobile networks.In M2M communication, the role of mobile network is largely confined toserve as a transport network. M2M devices or user equipment (UEs)coupled to a mobile network may be capable of replying to requests fordata contained within these types of UEs. These UEs may also be capableof transmitting data autonomously and parameters defining what or whendata is transmitted may be adjusted or updated responsive to triggermessages.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a communication system.

FIG. 2 illustrates an embodiment of a first message flow.

FIGS. 3A-D illustrates embodiments of additional message flows.

FIG. 4 illustrates an embodiment of a second message flow.

FIG. 5 illustrates an embodiment of a first apparatus and system.

FIG. 6 illustrates an embodiment of a second apparatus and system.

FIGS. 7A-B illustrate embodiments of logic flows.

FIG. 8 illustrates embodiments of storage media.

FIG. 9 illustrates an embodiment of user equipment.

FIG. 10 illustrates an embodiment of a device.

FIG. 11 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Various embodiments are generally directed to techniques for improvingwireless communications between devices in wireless networks, such as awireless network defined by one or more 3rd Generation PartnershipProject (3GPP) technologies and/or standards, for example. In someembodiments, a wireless network may operate in accordance with one ormore 3GPP Long Term Evolution (LTE), and/or 3GPP LTE-Advanced (LTE-A)technologies and/or standards. In one embodiment, for example, awireless network may operate in accordance with the 3GPP TechnicalSpecification (TS) 24.301 titled “Technical Specification Group CoreNetwork and Terminals; Non-Access-Stratum (NAS) protocol for EvolvedPacket System (EPS); Stage 3 (Release 14),” V14.1.0, September 2016(“3GPP Stage 3 Specification”), including any revisions, progeny, and/orvariants. Embodiments are not limited to these examples.

The 3GPP Stage 3 Specification defines protocols for mobility managementand session management between User Equipment (UE) and a MobilityManagement Entity (MME) in an Evolved Packet System (EPS). Theseprotocols typically belong to a non-access stratum (NAS). An EPSMobility Management (EMM) protocol provides procedures for the controlof mobility when a UE is using an Evolved Universal Terrestrial RadioAccess Network (E-UTRAN). The EMM protocol also provides control ofsecurity for the NAS protocols. An EPS Session Management (ESM) protocolprovides procedures for handling of EPS bearer contexts. Together withthe bearer control provided by the access stratum, the ESM protocol isused for control of user plane bearers.

Various embodiments implement techniques to create and/or improve EMMconnection management procedures as defined by, for example, section 5.6(among others) of the 3GPP Stage 3 Specification. For instance, oneembodiment implements techniques to create and/or improve one or moreservice request procedures as defined by section 5.6.1 (among others) ofthe 3GPP Stage 3 Specification. For instance, one embodiment implementstechniques to create and/or improve one or more service requestprocedures as defined by section 8.2 (among others) of the 3GPP Stage 3Specification.

A UE may send a service request message to a MME in accordance with oneor more service request procedures. A service request procedure managestransfer of a UE from an EMM-IDLE mode to an EMM-CONNECTED mode. A UE isin EMM-CONNECTED mode when a NAS signaling connection between a UE andnetwork is established. The term EMM-CONNECTED mode, for example, maycorrespond to the term ECM-CONNECTED state used in the 3GPP Stage 2Specification in TS 23.401. A UE is in an EMM-IDLE mode when no NASsignaling connection between a UE and network exists, or when a RRCconnection suspend has been indicated by lower layers. The term EMM-IDLEmode, for example, may correspond to the term ECM-IDLE state used in the3GPP Stage 2 Specification. If a UE is not using EPS services withcontrol plane Cellular Internet of Things (CIoT) EPS optimization, theservice request procedure is used to establish the radio and S1 bearerswhen user data or signaling is to be sent. The user data in this case issent over the user plane only. If a UE is using EPS services withcontrol plane CIoT EPS optimization, this procedure can be used for UEinitiated transfer of user data via the control plane. A UE typicallyinitiates or invokes service request procedures. However, a networkelement may also initiate or invoke service request procedures as well.This can be accomplished, for example, through a paging procedure.

A MME may send a SERVICE ACCEPT message to a UE in accordance with oneor more service request procedures. A service request procedure managesacceptance of a SERVICE ACCEPT message. For instance, a MME may send aSERVICE ACCEPT message to complete the service request procedureinitiated by a UE. Embodiments are not limited to this example.

Various embodiments may implement techniques to improve service requestprocedures in a wireless network arranged in accordance with the 3GPPStage 3 Specification. In one embodiment, for example, an apparatus maycomprise processing circuitry and computer-readable storage media havingstored thereon instructions for execution by the processing circuitry.The instructions, when executed by a UE operating in an Evolved PacketSystem (EPS) mobility management (EMM)-IDLE mode and configured to useEPS services with control plane CIoT EPS optimization, may determine toinitiate a service request procedure to enable a transfer of user datavia a control plane. The UE may generate a service request message, suchas a data service request message (e.g., DATA SERVICE REQUEST), thatcontains a service type information element (IE) comprising a servicetype value set to indicate either a mobile originating request or amobile terminating request. The UE may send the service request message(e.g., DATA SERVICE REQUEST) to a MME to initiate the service requestprocedure. Other embodiments are described and claimed.

Embodiments as described herein provide significant technicaladvantages. For instance, embodiments may support IoT and CIoTapplications, where mobile network operators need to address usagescenarios with devices that are power efficient over lengthy periods oftime, such as several years or decades. This can be particularlydifficult in challenging coverage conditions, such as when M2M or MTCdevices are located inside commercial buildings or residential homes.Furthermore, devices need to be at a price point where they can bedeployed on a massive scale and potentially disposable. As such,embodiments support highly efficient handling of frequent and infrequentsmaller data transmission with reduced overhead for system signaling inwireless networks. Furthermore, embodiments accomplish this whilemaintaining security, supporting power consumption optimizations,simplifying mobility and session management procedures, supportingpaging operations, and other network operations.

Various embodiments may comprise one or more elements. An element maycomprise any structure arranged to perform certain operations. Eachelement may be implemented as hardware, software, or any combinationthereof, as desired for a given set of design parameters or performanceconstraints. Although an embodiment may be described with a limitednumber of elements in a certain topology by way of example, theembodiment may include more or less elements in alternate topologies asdesired for a given implementation. It is worthy to note that anyreference to “one embodiment” or “an embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment. The appearances ofthe phrases “in one embodiment,” “in some embodiments,” and “in variousembodiments” in various places in the specification are not necessarilyall referring to the same embodiment.

FIG. 1 illustrates a communication system 100. In one embodiment, forexample, the communication system 100 may be implemented as a 3GPPsystem. Various devices and/or network entities of the communicationsystem 100 may implement techniques to improve service requestprocedures in accordance with the 3GPP Stage 3 Specification, asmodified using one or more of the principles described herein.

As shown in FIG. 1, the communication system 100 illustrates a varietyof components that may be used to provide communication services oraccess to one or more 3GPP devices. The communication system 100includes a UE 102 and an E-UTRAN 104. The E-UTRAN 104 may include one ormore evolved node B (eNB) 106. The communication system 100 may includemore or less devices as well.

In one embodiment, for example, the UE 102 and eNB 106 may beimplemented as narrowband devices configured to wirelessly communicatewith each other in accordance with a NB-LTE bandwidth. The NB-LTEbandwidth may generally comprise a bandwidth that is smaller than aminimum bandwidth that may be permitted in a conventional LTE system. Insome embodiments, the NB-LTE bandwidth may comprise a bandwidthcorresponding to one LTE physical resource block (PRB). In variousembodiments, the NB-LTE bandwidth may comprise a 180 kHz bandwidth. Insome embodiments, the NB-LTE bandwidth may comprise a 200 kHz bandwidth.It may be appreciated that although operating environment 100 as shownin FIG. 1 is described as a NB-LTE network, embodiments may also beimplemented in other types of wireless networks, such as various mobilebroadband wireless communications networks. The embodiments are notlimited in this context.

The communication system 100 also includes a core network 108communicatively coupled to the UE 102, E-UTRAN 104 and/or eNB 106. Thecore network 108 may comprise, for example, an evolved packet core (EPC)that includes an MME 110, a home subscriber server (HSS) 112, a servinggateway (SGW) 114, a packet data network (PDN) gateway (PGW) 116, aservice capability exposure function (SCEF) 118, a short message service(SMS) center (SMSC) 120, a gateway mobile location center (GMLC) 122,and a secure user plane location (SUPL) secure location platform (SLP)124, among other core network entities.

In general, the SGW 114 and PGW 116 may provide access to an operator'sinternet protocol (IP) services 126, which may provide access to one ormore third party servers 128, such as web servers or applicationservers. The SCEF 118 may provide one or more power saving modeparameters or enhanced power saving mode parameters to one or more otherinternal or external entities to allow for timed communication to the UE102 or to allow knowledge of a current availability of the UE 102. TheSMSC 120 may be configured to store, forward, convert and/or deliver SMSmessages. The SMSC 120 may include one or more of an SMS service center(SMS-SC), SMS gateway service center (SMS-GMSC), or other SMSinfrastructure or system to interface with SMS infrastructure. The GMLC122 may comprise a control-plane system that may be used to determine orprovide a location of a UE or other mobile station. The SLP 124 may be auser-plane system that may be used to determine or provide a location ofa UE or other mobile station.

In various embodiments, the communication system 100 may implementdevices having enhancements and optimizations for features andcapabilities relating to CIoT for connecting to an EPS network, such asdefined by the 3GPP Stage 3 Specification and techniques providedherein, for example. Similarly, the EPS network may also be enhanced forCIoT features, such as defined by the 3GPP Stage 3 Specification andtechniques provided herein, for example. Embodiments are not limited inthis context.

Certain CIoT features were defined in 3GPP TS 21.101 V13.0.0 (2016-12)titled “Technical Specification Group Services and System Aspects;Technical Specifications and Technical Reports for a UTRAN-based 3GPPsystem (Release 13),” dated December 2016 (“3GPP Release 13”). 3GPPRelease 13 specified a number of CIoT optimizations, including a controlplane EPS optimization (also referred to as “Data via MME”) and a userplane EPS optimization (also referred to as “User Plane Solution”).

One feature of the control plane EPS optimization results in new NASmessages to carry data (via MME), ciphering and integrity protection,Internet Protocol (IP) header compression at MME, and so forth. Duringidle to connected mode transitions, however, the optimizations do notestablish user plane connection. For the MT case, as shown in FIG.5.3.4B.3-1 in the 3GPP Stage 3 Specification, the paging message (asshown in steps 3 and 4) does not indicate whether the paging is due todownlink data from the user plane (e.g., a S1-U connection) or due tothe control plane (e.g., a SCEF connection). Therefore, based on justthe paging message, the UE is not aware whether user plane bearers arerequired to be established for MT data from control plane connections.In various embodiments, the paging message may be modified to containthis distinction, and may specific if user data is intended to bedelivered via a user plan or a control plane, as described in moredetail below.

One feature of the user plane EPS optimization results in storing eNBcontext in eNB and UE in an idle state. The UE may utilize new suspendand resume procedures. For instance, during a Suspend Connectionprocedure, the UE stores AS information as it transitions into anEMM-IDLE mode. The eNodeB stores AS information, a S1AP association anda bearer context for the UE. The MME stores the S1AP association and thebearer context for the UE and enters EMM-IDLE. During a ResumeConnection procedure, the UE resumes the connection with the networkusing the AS information stored during the Suspend Connection procedure,the eNodeB notifies the MME that the connection with the UE is resumed,and MME enters an EMM-CONNECTED mode.

Various embodiments propose modifications and updates to certainprocedures defined in the 3GPP Stage 3 Specification and/or 3GPP Release13. More particularly, some embodiments implement a way for handlingmobile terminated data transfer operations for narrowband (NB)-IoT orCIoT devices for both control plane and user plane optimizations.Embodiments also implement updates to a paging procedure for NB-IoT orCIoT devices for both control plane and user plane optimizations.

In one embodiment, for example, the MME 110 may send a paging messagethat includes a source of downlink data. Alternatively, the MME 110 mayleave a paging message unmodified. In either case, the UE 102 respondswith a new DATA SERVICE REQUEST message as part of an updated servicerequest procedure. If the UE 102 knows the source of downlink data, theUE 102 requests the MME 110 to establish appropriate bearers as part ofthe DATA SERVICE REQUEST message. If the UE 102 does not know the sourceof downlink data, the MME 110 sets up the appropriate bearers as itknows the source of downlink data. The UE 102 may use a timer todetermine whether the MME 110 has setup things appropriately.Alternatively, the MME 110 may explicitly send a new SERVICE ACCEPTmessage to the UE 102 with appropriate information.

To accomplish this, embodiments may implement a novel DATA SERVICEREQUEST message and a novel SERVICE ACCEPT message, and accompanyingprocedures. The new DATA SERVICE REQUEST message includes a deviceproperties IE for low priority IoT devices, and includes an ESM messagecontainer to piggyback an ESM message. This is at least 6 octets moreefficient than an EXTENDED SERVICE REQUEST message as it does notinclude a MME temporary mobile subscriber entity (TMSI) (M-TMSI).

For mobile terminated data transfer and paging operations, when the userdata is sent in EMM-CONNECTED mode, the UE 102 and the MME 110 use anESM message such as ESM DATA TRANSPORT to transfer data. When user datais to be sent in an uplink (UL) channel when the UE 102 is in anEMM-IDLE mode, the UE 102 uses a service request procedure and a new EMMmessage DATA SERVICE REQUEST as an initial NAS message. The DATA SERVICEREQUEST message includes a ciphered ESM message ESM DATA TRANSPORT in anew ESM message container IE. The DATA SERVICE REQUEST message may alsobe used without an ESM message container or with an empty ESM messagecontainer to respond to paging from the MME 110. The MME 110 in turnresponds with a SERVICE ACCEPT message to terminate the service requestprocedure.

By way of example, assume the UE 102 has enhancements and optimizationsfor features and capabilities relating to Cellular Internet of Things(CIoT) for connecting to an Evolved Packet System (EPS) network that isalso enhanced for CIoT features. The UE 102 may be configured to use EPSservices with control plane CIoT EPS optimization. The EPS network mayinclude network entities such as those identified in the core network108.

When operational within the communication system 100, assume the UE 102needs to transfer mobile originating (MO) data via a control plane tothe MME 110 and/or a network entity in the core network 108 (e.g.,configured as an EPS network) may need to transfer mobile terminating(MT) data via a control plane to the UE 102. The UE 102 may determine toinitiate a service request procedure to enable transfer of user data viaa control plane. The UE 102 may generate a service request message(e.g., DATA SERVICE REQUEST) that contains a service type informationelement (IE) comprising a service type value set to indicate either a MOrequest or a MT request. The UE 102 may send the service request messageto the MME 110 to initiate the service request procedure.

Assume the UE 102 is currently placed in an EMM-IDLE mode. An EMM entityin the UE 102 may initiate a data transfer procedure via the controlplane by sending a DATA SERVICE REQUEST message. The DATA SERVICEREQUEST message may include an ESM message container IE which containsdata to be sent in an ESM DATA TRANSPORT message. A data service type ofthe DATA SERVICE REQUEST message indicates a MO request. The DATASERVICE REQUEST message is ciphered and integrity protected, and sent tothe MME 110. The UE 102 may optionally include a supervision timer tomonitor success of the DATA SERVICE REQUEST message and the completionof the service request procedure. Alternatively, the UE 102 may wait foran explicit message from the MME 110 (such as a SERVICE ACCEPT messageor a SERVICE REJECT message) in response to the DATA SERVICE REQUESTmessage to complete the service request procedure.

When the MME 110 receives the ESM DATA TRANSPORT message, the MME 110identifies a bearer (e.g., a SCEF connection) on which to transfer theuser data inside the core network 108 based on the EPS bearer identityincluded in the ESM DATA TRANSPORT message. The MME 110 then forwardscontents (e.g., user data) of the ESM message container IE accordingly.On a successful transfer of container contents, the MME 110 sends aSERVICE ACCEPT message to the UE 102. The UE 102 in turn does notrelease the EPS bearer context. On an unsuccessful transfer of containercontents, the MME 110 sends a SERVICE REJECT message to the UE 102.

Just as the UE 102 may need to transfer MO data via a control plane tothe MME 110, one or more entities of the core network 108 may need totransfer mobile terminating (MT) data to the UE 102. In this case, theMME 110 may send a paging request to the UE 102 for MT data. Further,the network may indicate whether to “transfer user data via controlplane” or “transfer user data via user plane” based on preferencesand/or capabilities of the UE 102.

In some cases, a paging request may include a source of downlink data,such as a PGW 116 or SCEF 118, for example. When the UE 102 receives apaging message indicating a “transfer user data via the control plane,”the UE 102 may respond with a DATA SERVICE REQUEST message. A dataservice type of the DATA SERVICE REQUEST message may indicate a MTrequest. The UE 102 may also indicate to the MME 110 to setupappropriate CP/UP bearers based on the source of the downlink data(e.g., a connection). For instance, the paging message may includevarious parameters, such as a first parameter to indicate a source ofdownlink data, and a second parameter to indicate whether the controlplane or a data plane will transfer the user data.

In some cases, a paging request may omit the source of downlink data.When the UE 102 receives a paging message indicating a “transfer userdata via the control plane,” the UE 102 may respond with a DATA SERVICEREQUEST message. A data service type of the DATA SERVICE REQUEST messagemay indicate a MT request. When the MME 110 receives the DATA SERVICEREQUEST message with a data service type of MT request, the MME 110 maysend an ESM DATA TRANSPORT message. When the UE 102 receives the ESMDATA TRANSPORT message, the UE 102 may forward the container data to anupper layer of the network protocol stack using an EPS bearer identity.

Although the communication system 100 is described as a 3GPP system, itmay be appreciated that the communication system 100 may be implementedin accordance with other wireless standards and/or specifications aswell. The techniques disclosed herein may involve transmission of dataover one or more wireless connections using one or more wireless mobilebroadband technologies. Various embodiments may additionally oralternatively involve transmissions according to one or more GlobalSystem for Mobile Communications (GSM)/Enhanced Data Rates for GSMEvolution (EDGE), Universal Mobile Telecommunications System (UMTS)/HighSpeed Packet Access (HSPA), and/or GSM with General Packet Radio Service(GPRS) system (GSM/GPRS) technologies and/or standards, including theirrevisions, progeny and variants.

Examples of wireless mobile broadband technologies and/or standards mayalso include, without limitation, any of the Institute of Electrical andElectronics Engineers (IEEE) 802.16 wireless broadband standards such asIEEE 802.16m and/or 802.16p, International Mobile TelecommunicationsAdvanced (IMT-ADV), Worldwide Interoperability for Microwave Access(WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000(e.g., CDMA2000 1×RTT, CDMA2000 EV-DO, CDMA EV-DV, and so forth), HighPerformance Radio Metropolitan Area Network (HIPERMAN), WirelessBroadband (WiBro), High Speed Downlink Packet Access (HSDPA), High SpeedOrthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA),High-Speed Uplink Packet Access (HSUPA) technologies and/or standards,including their revisions, progeny and variants.

Some embodiments may additionally or alternatively involve wirelesscommunications according to other wireless communications technologiesand/or standards. Examples of other wireless communications technologiesand/or standards that may be used in various embodiments may include,without limitation, other IEEE wireless communication standards such asthe IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,IEEE 802.11u, IEEE 802.11ac, IEEE 802.11ad, IEEE 802.11af, and/or IEEE802.11ah standards, High-Efficiency Wi-Fi standards developed by theIEEE 802.11 High Efficiency WLAN (HEW) Study Group, Wi-Fi Alliance (WFA)wireless communication standards such as Wi-Fi, Wi-Fi Direct, Wi-FiDirect Services, Wireless Gigabit (WiGig), WiGig Display Extension(WDE), WiGig Bus Extension (WBE), WiGig Serial Extension (WSE) standardsand/or standards developed by the WFA Neighbor Awareness Networking(NAN) Task Group, machine-type communications (MTC) standards such asthose embodied in 3GPP Technical Report (TR) 23.887, 3GPP TechnicalSpecification (TS) 22.368, 3GPP TS 23.682, and/or 3GPP TS 24.301, and/ornear-field communication (NFC) standards such as standards developed bythe NFC Forum, MulteFire and MulteFire Alliance standards and/orspecifications such as MulteFire Specificaiton 1.0, including anyrevisions, progeny, and/or variants of any of the above. The embodimentsare not limited to these examples

In addition to transmission over one or more wireless connections, thetechniques disclosed herein may involve transmission of content over oneor more wired connections through one or more wired communicationsmedia. Examples of wired communications media may include a wire, cable,metal leads, printed circuit board (PCB), backplane, switch fabric,semiconductor material, twisted-pair wire, co-axial cable, fiber optics,and so forth. The embodiments are not limited in this context.

FIG. 2 illustrates an exemplary message flow 200 for the communicationsystem 100. More particularly, the message flow 200 illustrates handlingpaging for MT data transfer in the communication system 100. The messageflow 200 shows modifications to a paging procedure for a UE 102 enabledwith CIoT optimizations

In the communication system 100, upon reception of a paging indication,if the UE 102 is in an EMM-IDLE mode without suspend indication andcontrol plane CIoT EPS optimization is used by the UE 102, the UE 102may stop a timer T3346, if running, and initiate a service requestprocedure. If the UE 102 has uplink user data to send to the corenetwork 108 over the control plane via the MME 110 when receiving thepaging indication, the UE 102 may send a DATA SERVICE REQUEST message.This message may include an ESM message container IE which contains userdata to be sent in a ESM DATA TRANSPORT message.

In some embodiments, the MME 110 may include an indication in the pagingmessage as to a type of connection (e.g., data transfer) that has causedthe paging. For example, the paging can be due to downlink data from theuser plane (S1-U connection) or due to control plane (SCEF connection).The UE 102 can then respond appropriately with a DATA SERVICE REQUESTmessage and can ask the MME 110 to setup any relevant bearers.

In another embodiment, the MME 110 may not provide any indication as toa type of data that has caused paging. In this case, the UE 102 may justrespond with a DATA SERVICE REQUEST message, and it would be up to theMME 110 to setup any relevant bearers as part of the response. The MME110 may indicate setup information accordingly as part of a SERVICEACCEPT message.

An example of a paging procedure is specified in section 5.6.2 of the3GPP Stage 3 Specification. The paging procedure is used by the networkto request establishment or resumption of a NAS signaling connection tothe UE 102. According to section 5.6.2.2.1 of the 3GPP Stage 3Specification, upon reception of a paging indication, the UE 102 caninitiate one of two procedures: (1) a service request procedure; or (2)a tracking area update procedure when timer T3346 is running. Since apaging message does not explicitly indicate whether the paging wasinitiated due to downlink data from the control plane or the user plane,and generally timer T3346 will not be running, the UE 102 frequentlyuses a service request procedure. As such, on receipt of a pagingmessage, the UE 102 may respond with a new DATA SERVICE REQUEST messagewith a service type that indicates a MT request.

As shown in the message flow 200, for example, the MME 110 may send arequest for paging 210 to an access stratum (AS) 202. The MME 110 mayalso start timer T3413 or T3415. The AS 202 is a functional layer in theUMTS and LTE wireless telecommunications protocol stacks between a radionetwork and user equipment. It may comprise, for example, various ASprotocols. In general, the AS 202 is responsible for transporting dataover a wireless connection and managing radio resources. The AS 202 mayreceive request paging 210, and send a paging indication 212 to the UE102. The UE 102 may send a SERVICE REQUEST, an EXTENDED SERVICE REQUESTor a DATA SERVICE REQUEST message 214 to the MME 110. The MME 110 mayreceive the SERVICE REQUEST, the EXTENDED SERVICE REQUEST or the DATASERVICE REQUEST message, and stop timer T3413 or T3415. Note that, by3GPP convention, certain embodiments express message names in upper caseletters, and procedure names in lower case letters. However, embodimentsare not limited to this convention.

FIGS. 3A-D illustrate exemplary message flows 300, 320, 340 and 360,respectively, for the communication system 100. The message flows 300,320, 340 and 360 show various modifications to a service requestprocedure to handle MT data transfer for a CIoT device.

Since a network will not respond with setting up user plane bearers, theMME 110 responds with a new SERVICE ACCEPT message followed by an ESMDATA TRANSPORT message. The SERVICE ACCEPT and ESM DATA TRANSPORTmessages are ciphered and integrity protected. Alternatively, the ESMDATA TRANSPORT message could be included in an ESM message container IEincluded in the SERVICE ACCEPT message, and then only the SERVICE ACCEPTmessage would be integrity protected. When receiving the ESM DATATRANSPORT message, the UE 102 may forward container contents to upperlayers of the network protocol stack using an EPS bearer identityincluded in the ESM DATA TRANSPORT message.

As shown in the message flow 300, the UE 102 may initiate a servicerequest procedure by sending a DATA SERVICE REQUEST message 302 to theMME 110 via the AS 202. The UE 102 may also start a timer T3417. The MME110 may receive the DATA SERVICE REQUEST message 302, and respond with asecurity protected NAS message 304. Examples of a security protected NASmessage 304 may include without limitation a SECURITY MODE COMMAND, aSERVICE ACCEPT message, or an ESM DATA TRANSPORT message. The UE 102 mayreceive the security protected NAS message 304, and stop the timerT3417.

As shown in the message flow 320, the UE 102 may initiate a servicerequest procedure by sending a DATA SERVICE REQUEST message 322 to theMME 110 via the AS 202. The UE 102 may also start a timer T3417. The MME110 and/or the AS 202 may receive the DATA SERVICE REQUEST message 322.The AS 202 may respond with an AS indication message 324 withinformation about release of a radio resource control (RRC) connection.An AS indication message 324 may provide indications from lower layersand/or results of procedures triggered by the MME 110 in the servicerequest procedure. Triggered procedures could comprise, for example, aRRC connection release procedure or RRC connection reconfigurationprocedure, such as defined in 3GPP TS 36.331. The UE 102 may receive theAS indication message 324, and stop the timer T3417.

As shown in the message flow 340, the UE 102 may initiate a servicerequest procedure by sending a DATA SERVICE REQUEST message 342 to theMME 110 via the AS 202. The UE 102 may also start a timer T3417. The MME110 and/or the AS 202 may receive the DATA SERVICE REQUEST message 342.The AS 202 may respond with an AS indication message 344 withinformation about bearer establishment for the user plane. The UE 102may receive the AS indication message 344, and stop the timer T3417.

As shown in the message flow 360, the UE 102 may initiate a servicerequest procedure by sending a DATA SERVICE REQUEST message 362 to theMME 110 via the AS 202. The UE 102 may also start a timer T3417. The MME110 may receive the DATA SERVICE REQUEST message 362, and respond with aSERVICE REJECT message 364. For instance, on an unsuccessful transfer ofcontainer contents, the MME 110 may send the SERVICE REJECT message 364to the UE 102. The UE 102 may receive the SERVICE REJECT message 364,and stop the timer T3417.

FIG. 4 illustrates a message flow 400 for the communication system 100.The message flow 400 may illustrate a case where the MME 110 utilizesexplicit acknowledgements for a DATA SERVICE REQUEST message, such as aSERVICE ACCEPT or a SERVICE REJECT message.

FIG. 4 illustrates part of a message flow shown in 3GPP TSG SA WG2Meeting #112 titled “Introduction of Control Plane CIoT EPSoptimization,” Change Request (CR) 2942 to TS 23.401, Revision 13,Current Version 13.5.0, Feb. 23-26, 2016 (“S2-161170”). In stage 2(S2-161170), the message flow 400 includes message flow operations 1-13which are similar to those shown in FIG. 5.3.4B.2-1: MO Data transportin NAS PDU according to S2-161170, modified to further show an optionfor the MME 110 to reject a NAS DATA PDU. One design consideration for aservice request procedure is what should be used as a stop criterion fora MO service request procedure. One technique would be to use a layer 2acknowledgement for successful transmission of a RRC Connection SetupComplete (e.g., Service Request [User data]) as a stop criterion. Usingthis technique means that at the end of message flow operation 1, the UE102 assumes that the service request procedure has been completedsuccessfully.

At that point in time, however, the message has not yet reached the MME110. So it is unknown whether message flow operation 2 will actually beperformed successfully, and if so, how the MME 110 will then react. Oneadvantage for re-using a service request procedure in message flowoperation 1 is the re-use of an existing handling of unsuccessful andabnormal cases, as described in the 3GPP Stage 3 Specification,sub-clauses 5.6.1.5 and 5.6.1.6. However, according to a description ofan unsuccessful case, the MME 110 can respond to a service request withSERVICE REJECT message 402, 404 as shown in message flow operations A,B. This would indicate when the outcome of the service request procedurewas not successful. If that is the case, then it may not be necessary todefine receipt of a layer 2 acknowledgement for the initial servicerequest as criterion for successful completion of the service requestprocedure.

Two options can be used as stop criterion for a service requestprocedure. A first option is use of a supervision timer. A second optionis a positive acknowledgement from the MME 110 (e.g., a SERVICE ACCEPTmessage).

A first option for use as a stop criterion for a service requestprocedure is use of a supervision timer. The supervision timer should bedimensioned so that the UE 102 can be sure that it will not receive aSERVICE REJECT message after expiry of the timer. For instance, thesupervision timer should factor in a time for transfer of a S1AP (e.g.,Initial UE (Service Request)) to the MME 110 as shown in message flowoperation 2 of the message flow 400. The supervision timer should alsofactor in some time for processing of the message, which includesdetection that a subscriber context is unknown. The supervision timershould also factor in some time for transmission of a SERVICE REJECTmessage as part of the DL S1-AP message 402 sent from the MME 110 to theeNB 106 (e.g., message flow operation A), and the SERVICE REJECT messageas part of a RRC DL message 404 sent from the eNB 106 to the UE 102(e.g., message flow operation B).

For a final transfer via the radio interface, a worst case scenarioshould be assumed, which includes a maximum number of retransmissionsthat can occur under “enhanced coverage” conditions. In contrast, if theMME 110 responds with a SERVICE ACCEPT message, then for message flowoperation B the UE 102 will only need to wait for an “average number” ofretransmissions, which could be approximately half of a maximum numberof retransmissions. A difference between an assumed worst case scenarioand an average case the UE 102 will experience in operation willtypically be on the order of seconds. For instance, with a SERVICEACCEPT message, the UE 102 can on average consider a service requestprocedure as successfully completed several seconds earlier than withoutsuch a message.

It is worthy to note that expiry of a supervision timer does notnecessarily guarantee that the MME 110 has actually received a DATASERVICE REQUEST message with user data. If an application sends only oneUL packet, and nothing is sent by an application server in return, thena next message the UE 102 is going to receive after having sent the DATASERVICE REQUEST message is an RRCConnectionRelease message. Currently,this message can only indicate the following ReleaseCauses:loadBalancingTAUrequired, other, and cs-FallbackHighPriority. To providean indication that the user data has actually been received by the MME110, a new value for the ReleaseCause can be defined, such asReleaseCauses: DataReceived. In this case, a corresponding S1AP Causeshould be defined as well.

A second option for use as a stop criterion for a service requestprocedure is use of a positive acknowledgement from the MME 110, such asa SERVICE ACCEPT message. The SERVICE ACCEPT message results in apositive acknowledgement from the MME 110. This provides significantadvantages. The SERVICE ACCEPT message adds an explicit synchronizationof EPS bearer contexts to the service request procedure. For instance,the UE 102 could include an EPS bearer context status IE in the DATASERVICE REQUEST message, as it can for an EXTENDED SERVICE REQUEST. TheMME 110 could include a same or similar IE in the SERVICE ACCEPT orSERVICE REJECT messages, respectively.

Furthermore, if the UE 102 attempts to send user data via the controlplane for an EPS bearer identity, for which the MME 110 does not have anEPS bearer context and/or PDN connection, then the MME 110 could respondwith the following messages:

-   -   1. SERVICE REJECT (EMM cause=“implicitly detached”), if this was        the last PDN connection and the MME does not support        EMM-REGISTERED without PDN connection;    -   2. SERVICE REJECT (EMM cause=“ESM failure”, [ESM Status (ESM        cause=“invalid EPS bearer identity”)]) and release the RRC        connection; and/or    -   3. SERVICE ACCEPT (EMM cause=“ESM failure”, [ESM Status (ESM        cause=“invalid EPS bearer identity”)]) and keep the RRC        connection to enable the UE to reactivate the PDN connection.

FIG. 5 illustrates a block diagram of an apparatus 500. Apparatus 500may be representative of a UE that implements techniques for UEinitiated IP flow mobility and/or responding to network initiated IPflow mobility. As such, apparatus 500 may implement portions of themessage flows described in relation to FIGS. 2-4 that involve the UE 102as described therein, including the generation, transmission, reception,and processing of messages involving the UE 102.

As shown in FIG. 5, apparatus 500 can comprise multiple elementsincluding a processor circuit 502, a memory unit 504, a communicationscomponent 506, and a management component 508. The embodiments, however,are not limited to the type, number, or arrangement of elements shown inthis figure.

In some embodiments, apparatus 500 may comprise processor circuit 302.Processor circuit 502 may be implemented using any processor or logicdevice, such as a complex instruction set computer (CISC)microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, anx86 instruction set compatible processor, a processor implementing acombination of instruction sets, a multi-core processor such as adual-core processor or dual-core mobile processor, or any othermicroprocessor or central processing unit (CPU). Processor circuit 502may also be implemented as a dedicated processor, such as a controller,a microcontroller, an embedded processor, a chip multiprocessor (CMP), aco-processor, a digital signal processor (DSP), a network processor, amedia processor, an input/output (I/O) processor, a media access control(MAC) processor, a radio baseband processor, an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), aprogrammable logic device (PLD), and so forth. In one embodiment, forexample, processor circuit 502 may be implemented as a general purposeprocessor, such as a processor made by Intel® Corporation, Santa Clara,Calif. The embodiments are not limited in this context.

In various embodiments, apparatus 500 may comprise or be arranged tocommunicatively couple with a memory unit 504. Memory unit 504 may beimplemented using any machine-readable or computer-readable mediacapable of storing data, including both volatile and non-volatilememory. For example, memory unit 504 may include read-only memory (ROM),random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM(DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM(PROM), erasable programmable ROM (EPROM), electrically erasableprogrammable ROM (EEPROM), flash memory, polymer memory such asferroelectric polymer memory, ovonic memory, phase change orferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, or any other type of media suitablefor storing information.

It is worthy of note that some portion or all of memory unit 504 may beincluded on the same integrated circuit as processor circuit 502, oralternatively some portion or all of memory unit 504 may be disposed onan integrated circuit or other medium, for example a hard disk drive,that is external to the integrated circuit of processor circuit 502.Although memory unit 504 is comprised within apparatus 500 in FIG. 5,memory unit 504 may be external to apparatus 500 in some embodiments.The embodiments are not limited in this context.

In various embodiments, apparatus 500 may comprise a communicationscomponent 506. Communications component 506 may comprise logic,circuitry, and/or instructions operative to send messages to one or moreremote devices and/or to receive messages from one or more remotedevices. In some embodiments, communications component 506 may beoperative to send and/or receive messages over one or more wiredconnections, one or more wireless connections, or a combination of both.In various embodiments, communications component 506 may additionallycomprise logic, circuitry, and/or instructions operative to performvarious operations in support of such communications. Examples of suchoperations may include selection of transmission and/or receptionparameters and/or timing, packet and/or protocol data unit (PDU)construction and/or deconstruction, encoding and/or decoding, errordetection, and/or error correction. The embodiments are not limited tothese examples.

In some embodiments, apparatus 500 may comprise a management component508. Management component 508 may comprise logic, circuitry, and/orinstructions operative to manage functional operations of the apparatus500 including directing the communications component 506 to generate andtransmit messages and/or to receive and process messages. Theembodiments are not limited in this context.

FIG. 5 also illustrates a block diagram of a system 520. System 520 maycomprise any of the aforementioned elements of apparatus 500. System 520may further comprise a radio frequency (RF) transceiver 522. RFtransceiver 522 may comprise one or more radios capable of transmittingand receiving signals using various suitable wireless communicationstechniques. Such techniques may involve communications across one ormore wireless networks. Exemplary wireless networks include (but are notlimited to) cellular radio access networks, wireless local area networks(WLANs), wireless personal area networks (WPANs), wireless metropolitanarea network (WMANs), and satellite networks. In communicating acrosssuch networks, RF transceiver 522 may operate in accordance with one ormore applicable standards in any version. The embodiments are notlimited in this context.

In various embodiments, system 520 may comprise one or more RF antennas524. Examples of any particular RF antenna 524 may include, withoutlimitation, an internal antenna, an omni-directional antenna, a monopoleantenna, a dipole antenna, an end-fed antenna, a circularly polarizedantenna, a micro-strip antenna, a diversity antenna, a dual antenna, atri-band antenna, a quad-band antenna, and so forth. In someembodiments, RF transceiver 522 may be operative to send and/or receivemessages and/or data using one or more RF antennas 524. The embodimentsare not limited in this context.

In various embodiments, system 520 may comprise a display 526. Display526 may comprise any display device capable of displaying informationreceived from processor circuit 502. Examples for display 526 mayinclude a television, a monitor, a projector, and a computer screen. Inone embodiment, for example, display 526 may be implemented by a liquidcrystal display (LCD), light emitting diode (LED) or other type ofsuitable visual interface. Display 526 may comprise, for example, atouch-sensitive display screen (“touchscreen”). In some implementations,display 526 may comprise one or more thin-film transistors (TFT) LCDincluding embedded transistors. The embodiments, however, are notlimited to these examples.

In various embodiments, communications component 506 may be operative totransmit and receive messages with an eNB 106, as depicted and describedin relation to FIGS. 1-4. Communication with the eNB 106 can beimplemented over a wireless connection 530 (e.g., a wireless dataconnection) in accordance with one or more cellular communicationprotocols. The eNB 106 may be operative to transmit and receive messageswith the MME 110, as depicted and described in relation to FIGS. 1-4.Communication with the MME 110 can be implemented using a connection 540(e.g., wired or wireless data connections) in accordance with one ormore cellular communication protocols and/or network protocols.

In various embodiments, the management component 508 may implementtechniques to improve service request procedures service requestprocedure in the communication system 100 arranged in accordance withthe 3GPP Stage 3 Specification. The management component 508 can includea service request component 510.

In one embodiment, for example, the service request component 510 may beimplemented by the UE 102 as the apparatus 500 and/or system 520. Theservice request component 510 may comprise computer-readable storagemedia having stored thereon instructions for execution by the processorcircuitry 502. The instructions, when executed by the processorcircuitry of the UE 102 operating in an EMM-IDLE mode and configured touse EPS services with control plane CIoT EPS optimization, may determineto initiate a service request procedure to enable a transfer of userdata via a control plane. The service request component 510 may generatea message used by the service request procedure 512 that contains aservice type IE 514. The service type IE 514 may comprise a service typevalue 515 set to indicate either a mobile originating (MO) request or amobile terminating (MT) request. The service request component 510 maysend the service request message 512 to the MME 110 via the eNB 106, inorder to initiate the service request procedure. An example of a servicerequest message 512 may comprise a DATA SERVICE REQUEST message.Embodiments are not limited to this example.

In one embodiment, the service request component 510 may identify userdata to be sent to the MME 110. The service request component 510 mayinclude an ESM DATA TRANSPORT (EDT) message 517 in the service requestmessage 512, the ESM DATA TRANSPORT message 517 to comprise the userdata.

In one embodiment, the service request component 510 may generate theservice request message 512 to include an ESM message container IE 516containing the ESM DATA TRANSPORT message 517.

In one embodiment, the service request component 510 may determine toinitiate the service request procedure in response to a determinationthat uplink user data is pending at the UE. The service requestcomponent 510 may set the service type value 515 to indicate a MOrequest.

In one embodiment, the service request component 510 may determine toinitiate the service request procedure in response to receipt of apaging message. The service request component 510 may set the servicetype value 515 to indicate a MT request.

In one embodiment, the service request component 510 may determine thatthe service request procedure has been successfully completed based onreceipt of a security protected non-NAS message 518 from the MME 110.For example, the security protected NAS message 518 may comprise aservice accept message, a security mode command message, an ESM datatransport message, a service reject message, or other type of servicerequest procedure message. Embodiments are not limited in this context.

In one embodiment, the service request component 510 may identify one ormore EPS bearer contexts that an EPS bearer context status IE comprisedin the service accept message indicates as being inactive. The servicerequest component 510 may locally deactivate the identified one or moreEPS bearer contexts.

In one embodiment, the service request component 510 may cause the UE102 to enter an EMM-REGISTERED state in response to a determination thatthe service request procedure has been successfully completed.

In one embodiment, the service request component 510 may reset a servicerequest attempt counter in response to a determination that the servicerequest procedure has been successfully completed.

In one embodiment, the service request component 510 may control a timerT3417 for the service request procedure. For instance, the servicerequest component 510 may start the timer T3417 when a service requestmessage is sent. The service request component 510 may stop the timerT3417 in response to a determination that the service request procedurehas been successfully completed.

FIG. 6 illustrates a block diagram of an apparatus 600. Apparatus 600may be representative of the MME 110 and/or the AS 202 that implementstechniques for service request procedures. As such, apparatus 600 mayimplement portions of the message flows described in relation to FIGS.2-4 that involve the MME 110 and/or the AS 202 as described therein,including the generation, transmission, reception and processing ofmessages involving the MME 110 and/or the AS 202. As shown in FIG. 6,apparatus 600 can comprise multiple elements including a processorcircuit 602, a memory unit 604, a communications component 606, and adiscovery management component 608. The embodiments, however, are notlimited to the type, number, or arrangement of elements shown in thisfigure.

In some embodiments, the apparatus 600 may comprise processor circuit602. Processor circuit 602 may be implemented using any processor orlogic device, such as a complex instruction set computer (CISC)microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, anx86 instruction set compatible processor, a processor implementing acombination of instruction sets, a multi-core processor such as adual-core processor or dual-core mobile processor, or any othermicroprocessor or central processing unit (CPU). Processor circuit 602may also be implemented as a dedicated processor, such as a controller,a microcontroller, an embedded processor, a chip multiprocessor (CMP), aco-processor, a digital signal processor (DSP), a network processor, amedia processor, an input/output (I/O) processor, a media access control(MAC) processor, a radio baseband processor, an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), aprogrammable logic device (PLD), and so forth. In one embodiment, forexample, processor circuit 602 may be implemented as a general purposeprocessor, such as a processor made by Intel® Corporation, Santa Clara,Calif. The embodiments are not limited in this context.

In various embodiments, apparatus 600 may comprise or be arranged tocommunicatively couple with a memory unit 604. Memory unit 604 may beimplemented using any machine-readable or computer-readable mediacapable of storing data, including both volatile and non-volatilememory. For example, memory unit 604 may include read-only memory (ROM),random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM(DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM(PROM), erasable programmable ROM (EPROM), electrically erasableprogrammable ROM (EEPROM), flash memory, polymer memory such asferroelectric polymer memory, ovonic memory, phase change orferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, or any other type of media suitablefor storing information. It is worthy of note that some portion or allof memory unit 604 may be included on the same integrated circuit asprocessor circuit 602, or alternatively some portion or all of memoryunit 604 may be disposed on an integrated circuit or other medium, forexample a hard disk drive, that is external to the integrated circuit ofprocessor circuit 602. Although memory unit 604 is comprised withinapparatus 600 in FIG. 6, memory unit 604 may be external to apparatus600 in some embodiments. The embodiments are not limited in thiscontext.

In various embodiments, apparatus 600 may comprise a communicationscomponent 606. Communications component 606 may comprise logic,circuitry, and/or instructions operative to send messages to one or moreremote devices and/or to receive messages from one or more remotedevices. In some embodiments, communications component 606 may beoperative to send and/or receive messages over one or more wiredconnections, one or more wireless connections, or a combination of both.In various embodiments, communications component 606 may additionallycomprise logic, circuitry, and/or instructions operative to performvarious operations in support of such communications. Examples of suchoperations may include selection of transmission and/or receptionparameters and/or timing, packet and/or protocol data unit (PDU)construction and/or deconstruction, encoding and/or decoding, errordetection, and/or error correction. The embodiments are not limited tothese examples.

In some embodiments, apparatus 600 may comprise a management component608. Management component 608 may comprise logic, circuitry, and/orinstructions operative to manage functional operations of the apparatus600 including directing the communications component 606 to generate andtransmit messages and/or to receive and process messages. Theembodiments are not limited in this context.

FIG. 6 also illustrates a block diagram of a system 616. System 616 maycomprise any of the aforementioned elements of apparatus 600. System 616may further comprise a transceiver 618. Transceiver may be capable oftransmitting and receiving signals using various suitable communicationstechniques. Such techniques may involve communications across one ormore wired networks. In communicating across such networks, thetransceiver 618 may operate in accordance with one or more applicablestandards in any version. The embodiments are not limited in thiscontext.

In various embodiments, communications component 606 may be operative totransmit and receive messages with AS 202 as depicted and described inrelation to FIGS. 2-4. Communication with the AS 202 can be implementedover a communications link 622 as referenced in relation to the messageflows depicted and described in relation to FIGS. 2-4. Further, thecommunications component 606 may be operative to transmit and receivemessages with the UE 102 as depicted and described in relation to FIGS.2-5. Communication with the UE 102 can be implemented using acommunications link 626 as referenced in relation to the message flowsdepicted and described in relation to FIGS. 2-4. Similarly, the UE 102and AS 202 can communicate over the communications link 628 asreferenced in relation to the message flows depicted and described inrelation to FIGS. 2-4. Communications component 606 may also beoperative to transmit and receive messages with the IP services 126and/or servers 128 of the communication system 100 as depicted anddescribed in relation to FIG. 1.

In various embodiments, the management component 608 may implementtechniques to improve service request procedures and service requestprocedures in the communication system 100 arranged in accordance withthe 3GPP Stage 3 Specification. The management component 608 can includea service response component 610.

In one embodiment, for example, the service response component 610 maybe implemented by the MME 110 as the apparatus 600 and/or system 616.The service response component 610 may comprise computer-readablestorage media having stored thereon instructions for execution by theprocessor circuit 602. The instructions, when executed by the processorcircuit 602 of the MME 110 configured to use EPS services with controlplane CIoT EPS optimization, may access a service request message 512received from the UE 102 via the transceiver 618. The service requestmessage may contain a service type IE 514. The service responsecomponent 610 may identify a service type value 515 within the servicetype IE 514. The service response component 610 may initiate a transportof user data to the UE 102 via a control plane in response to adetermination that the service type value 515 indicates a MT request.

In one embodiment, for example, the service response component 610 maysend an ESM data transport message 517 to the UE 102, with the ESM datatransport message 517 containing the user data.

In one embodiment, for example, the service response component 610 maydetect a presence of an ESM message container IE 516 within the servicerequest message 512. The service response component 610 may forwardcontents of the ESM message container IE 516. The contents of the ESMmessage container IE 516 may comprise the ESM data transport message 517containing user data originating from the UE 102.

In one embodiment, for example, the service response component 610 maysend a security protected non-NAS message 518 to the UE 102. Forexample, the security protected NAS message 518 may comprise a SERVICEACCEPT message, a security mode command message, an ESM DATA TRANSPORTmessage, a SERVICE REJECT message, or other type of service requestprocedure message. A particular type of security protected NAS message518 sent may be selected, in part, as a result of a determination that aservice request procedure has been successfully completed orunsuccessfully completed.

As previously discussed, a network element may also initiate or invokeservice request procedures as well. This can be accomplished, forexample, through a paging procedure. In one embodiment, for example, themanagement component 608 of the MME 110 may send a paging message 612 tothe UE 102 in order to initiate or invoke service request procedures.The paging message 612 may optionally include a source type IE 614. Thesource type IE 614 may include a source type value 615. The source typevalue 615 may indicate a source of downlink data. Examples of sources ofdownlink data may include without limitation a PGW 116 or SCEF 118.Alternatively, the management component 608 may send a paging message612 without the source type IE 614 and source type value 615, or withthe source type IE 614 and the source type value 615 set to a defaultvalue indicating there is no source of downlink data identified by thesource type IE 614.

Operations for the above embodiments may be further described withreference to the following figures and accompanying examples. Some ofthe figures may include a logic flow. Although such figures presentedherein may include a particular logic flow, it can be appreciated thatthe logic flow merely provides an example of how the generalfunctionality as described herein can be implemented. Further, the givenlogic flow does not necessarily have to be executed in the orderpresented unless otherwise indicated. In addition, the given logic flowmay be implemented by a hardware element, a software element executed bya processor, or any combination thereof. The embodiments are not limitedin this context.

FIG. 7A illustrates an example of a logic flow 700 that may berepresentative of one or more of the disclosed air interface resourceutilization techniques for wireless communication networks according tovarious embodiments. For example, logic flow 700 may be representativeof operations that may be performed by the UE 102 as depicted anddescribed in FIGS. 1-4.

As shown in FIG. 7A, the logic flow 700 may access a paging messagereceived while the UE is in an Evolved Packet System (EPS) mobilitymanagement (EMM)-IDLE state and using EPS services with control planeCellular Internet of Things (CIoT) EPS optimization at block 702. Forinstance, the UE 102 may access a paging message 612 received while theUE 102 is in an EMM-IDLE state and using EPS services with control planeCIoT EPS optimization in accordance with one or more 3GPP techniques.

The logic flow 700 may determine, based on the paging message, that aMME has user data to send to the UE at block 704. For instance, the UE102 may determine, based on the paging message 612, that the MME 110 hasuser data to send to the UE 102.

The logic flow 700 may send a service request message to the MME toinitiate a service request procedure to enable the UE to receive theuser data via a control plane at block 706. For instance, the UE 102 maysend a service request message 512 to the MME 110 to initiate a servicerequest procedure to enable the UE 102 to receive the user data via acontrol plane of the wireless connections 530, 540.

FIG. 7B illustrates an example of a logic flow 720 that may berepresentative of one or more of the disclosed air interface resourceutilization techniques for wireless communication networks according tovarious embodiments. For example, logic flow 720 may be representativeof operations that may be performed by the MME 110 and/or the AS 202 asdepicted and described in FIGS. 1-4.

As shown in FIG. 7B, the logic flow 720 may access, at a mobilitymanagement entity (MME), a service request message received from userequipment (UE), the service request message to contain a service typeinformation element (IE) at block 722. For instance, the MME 110 mayaccess a service request message 512 received from the UE 102, theservice request message 512 to contain a service type IE 514.

The logic flow 720 may identify a service type value comprised in theservice type IE at block 724. For instance, the MME 110 may identify aservice type value 515 indicted in the service type IE 514.

The logic flow 720 may initiate a transport of user data to the UE via acontrol plane in response to a determination that the service type valueindicates a mobile terminating request at block 726. For instance, theMME 110 may initiate a transport of user data to the UE 102 via acontrol plane in response to a determination that the service type value515 indicates a MT request.

As previously discussed, various embodiments may implement techniques toimprove service request procedures in a wireless network arranged inaccordance with the 3GPP Stage 3 Specification. In one embodiment, forexample, updates to the 3GPP Stage 3 Specification may comprise thefollowing description.

5.6.1.2 Service Request Procedure Initiation

5.6.1.2.2 UE is Using EPS Services with CP-CIoTEPS Optimization

The UE shall send a DATA SERVICE REQUEST message, start T3417 and enterthe state EMM-SER VICE-REQ UEST-INITIATED.

For case a in subclause 5.6.1.1, the data service type of the DATASERVICE REQUEST message shall indicate “mobile terminating request”. TheUE shall set the length indicator of the ESM message container IE tozero and not include any ESM message.

For case b in subclause 5.6.1.1, the data service type of the DATASERVICE REQUEST message shall indicate “mobile originating request”. TheUE shall include an ESM DATA TRANSPORT message in the ESM messagecontainer IE.

For case c in subclause 5.6.1.1, the data service type of the DATASERVICE REQUEST message shall indicate “mobile originating request”. TheUE shall set the length indicator of the ESM message container IE tozero and not include any ESM message.

5.6.1.4.2 UE is Using EPS Services with CP-CIoT EPS Optimization

For case a in subclause 5.6.1.1, upon receipt of the DATA SERVICEREQUEST message with data service type indicating “mobile terminatingrequest”, the MME may:

1) initiate the transport of user data via the control plane procedureor any other NAS signalling procedure; or

2) if supported by the UE and required by the network, initiate thesetup of the user plane radio bearer(s).

For case b in subclause 5.6.1.1, upon receipt of the DATA SERVICEREQUEST message with data service type indicating “mobile originatingrequest” and with a non-empty ESM message container IE, the MME shallforward the contents of the ESM message container IE to the ESM layer.After completion of the EMM common procedures according to subclause5.6.1.3, if any, the MME may:

1) upon receipt of an “end-of-data-exchange” indication from the ESMlayer (see subclause 6.6.X.2 [CR 2324]), unless the MME has additionaldownlink user data or signalling pending, initiate release of the NASsignalling connection;

2) if downlink user data are pending, send an ESM DATA TRANSPORT messageto the UE or, if supported by the UE and required by the network,initiate the setup of the user plane radio bearer(s);

3) if downlink signalling is pending, send a signalling message to theUE; or

4) if no EMM common procedures were initiated and no downlink user dataor signalling are pending, or if the MME needs to perform an EPS bearercontext status synchronization, send a SERVICE ACCEPT message.

For case c in subclause 5.6.1.1, upon receipt of the DATA SERVICEREQUEST message with data service type indicating “mobile originatingrequest” and with an empty ESM message container IE, after completion ofthe EMM common procedures according to subclause 5.6.1.3, if any, theMME may:

1) if downlink user data are pending, send an ESM DATA TRANSPORT messageto the UE or, if supported by the UE and required by the network,initiate the setup of the user plane radio bearer(s);

2) if downlink signalling is pending, send a signalling message to theUE; or

3) if no EMM common procedures were initiated and no downlink user dataor signalling are pending, or if the MME needs to perform an EPS bearercontext status synchronization, send a SERVICE ACCEPT message.

For cases a, b and c in subclause 5.6.1.1, if the EPS bearer contextstatus IE is included in the DATA SERVICE REQUEST message, the networkshall deactivate all those EPS bearer contexts locally (withoutpeer-to-peer signalling between the network and the UE) which are activeon the network side but are indicated by the UE as being inactive. If adefault EPS bearer context is marked as inactive in the EPS bearercontext status IE included in the DATA SERVICE REQUEST message, and thisdefault bearer is not associated with the last PDN connection of the UEin the MME, the MME shall locally deactivate all EPS bearer contextsassociated to the PDN connection with the default EPS bearer contextwithout peer-to-peer ESM signalling to the UE. If the default bearer isassociated with the last remaining PDN connection of the UE in the MME,and EMM-REGISTERED without PDN connection is supported by the UE and theMME, the MME shall locally deactivate all EPS bearer contexts associatedto the PDN connection with the default EPS bearer context withoutpeer-to-peer ESM signalling to the UE.

If the EPS bearer context status IE is included in the DATA SERVICEREQUEST, the MME shall include an EPS bearer context status IE in theSERVICE ACCEPT message, indicating which EPS bearer contexts are activein the MME except for the case no EPS bearer context exists on thenetwork side.

If the MME needs to initiate an EPS bearer context statussynchronization, the MME may include an EPS bearer context status IE inthe SERVICE ACCEPT message also if no EPS bearer context status IE wasincluded in the DATA SERVICE REQUEST message.

For cases a, b and c in subclause 5.6.1.1, the UE shall treat thereceipt of a security protected NAS message or the indication from thelower layers that the user plane radio bearers are set up as successfulcompletion of the procedure. The UE shall reset the service requestattempt counter, stop the timer T3417 and enter the stateEMM-REGISTERED.

NOTE: The security protected NAS message can be e.g. a SECURITY MODECOMMAND, SERVICE ACCEPT or ESM DATA TRANSPORT message.

For case b in subclause 5.6.1.1 the UE shall also treat the indicationfrom the lower layers that the RRC connection has been released assuccessful completion of the procedure. The UE shall reset the servicerequest attempt counter, stop the timer T3417 and enter the stateEMM-REGISTERED.

Editor's note [WI CIoT-CT; CR #2395]: For cases a and c, an RRCconnection release in response to a DATA SERVICE REQUEST can beconsidered as abnormal case. The details are FFS.

For cases a, b and c in subclause 5.6.1.1, if the UE receives an EPSbearer context status IE included in the SERVICE ACCEPT message, the UEshall deactivate all those EPS bearers contexts locally (withoutpeer-to-peer signaling between the UE and the MME) which are active inthe UE, but are indicated by the MME as being inactive. If a default EPSbearer context is marked as inactive in the EPS bearer context status IEincluded in the SERVICE ACCEPT message, and this default bearer is notassociated with the last remaining PDN connection in the UE, the UEshall locally deactivate all EPS bearer contexts associated to the PDNconnection with the default EPS bearer context without peer-to-peer ESMsignaling to the MME. If the default bearer is associated with the lastremaining PDN connection of the UE in the MME, and EMM-REGISTEREDwithout PDN connection is supported by the UE and the MME, the UE shalllocally deactivate all EPS bearer contexts associated to the PDNconnection with the default EPS bearer context without peer-to-peer ESMsignaling to the MME.

If an EPS bearer context status IE is included in the SERVICE ACCEPTmessage, the UE may choose to ignore all those EPS bearers which areindicated by the MME as being active, but are inactive at the UE.

8.2.Y Service Accept

8.2. Y.1 Message Definition

This message is sent by the network in response to the Data ServiceRequest message. See table 8.2.Y.1.

Message type: SERVICE ACCEPT

Significance: dual

Direction: network to UE

TABLE 8.2.Y.1 SERVICE ACCEPT message content IEI Information ElementType/Reference Presence Format Length Protocol Protocol M V ½discriminator discriminator 9.2 Security header Security header M V ½type type 9.3.1 Service accept Message type M V 1 message identity 9.857 EPS bearer EPS bearer O TLV 4 context status context status 9.9.2.1

8.2.Y.2 EPS Bearer Context Status

This IE shall be included if the network wants to indicate the EPSbearer contexts that are active for the UE in the network.

FIG. 8 illustrates an embodiment of a storage medium 800. Storage medium800 may comprise any non-transitory computer-readable storage medium ormachine-readable storage medium, such as an optical, magnetic orsemiconductor storage medium. In various embodiments, storage medium 800may comprise an article of manufacture. In some embodiments, storagemedium 800 may store computer-executable instructions, such ascomputer-executable instructions to implement logic for the messageflows 200, 300, 320, 340 and/or 360 of FIGS. 2-4, and/or the logic flow700 of FIG. 7A. Examples of a computer-readable storage medium ormachine-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples ofcomputer-executable instructions may include any suitable type of code,such as source code, compiled code, interpreted code, executable code,static code, dynamic code, object-oriented code, visual code, and thelike. The embodiments are not limited in this context.

FIG. 8 also illustrates an embodiment of a storage medium 850. Likestorage medium 800, storage medium 850 may comprise any non-transitorycomputer-readable storage medium or machine-readable storage medium,such as an optical, magnetic or semiconductor storage medium. Examplesof such a computer-readable storage medium or machine-readable storagemedium may include—without limitation—any of the examples mentionedabove in reference to storage medium 800. In various embodiments,storage medium 850 may comprise an article of manufacture. In someembodiments, storage medium 850 may store computer-executableinstructions, such as computer-executable instructions to implementlogic for the message flows 200, 300, 320, 340 and/or 360 of FIGS. 2-4,and/or the logic flow 720 of FIG. 7B. Examples of suchcomputer-executable instructions may include—without limitation—any ofthe examples mentioned above in reference to storage medium 800. Theembodiments are not limited in this context.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware. Embodiments describedherein may be implemented into a system using any suitably configuredhardware and/or software.

FIG. 9 illustrates an example of a UE device 900 that may berepresentative of a UE that implements one or more of the disclosed airinterface resource utilization techniques for wireless communicationnetworks according to various embodiments. For example, UE device 900may be representative of NB-UE 104 according to some embodiments. Insome embodiments, the UE device 900 may include application circuitry902, baseband circuitry 904, Radio Frequency (RF) circuitry 906,front-end module (FEM) circuitry 908 and one or more antennas 910,coupled together at least as shown.

The application circuitry 902 may include one or more applicationprocessors. For example, the application circuitry 902 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith and/or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsand/or operating systems to run on the system.

The baseband circuitry 904 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 904 may include one or more baseband processorsand/or control logic to process baseband signals received from a receivesignal path of the RF circuitry 906 and to generate baseband signals fora transmit signal path of the RF circuitry 906. Baseband processingcircuitry 904 may interface with the application circuitry 902 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 906. For example, in some embodiments,the baseband circuitry 904 may include a second generation (2G) basebandprocessor 904 a, third generation (3G) baseband processor 904 b, fourthgeneration (4G) baseband processor 904 c, and/or other basebandprocessor(s) 904 d for other existing generations, generations indevelopment or to be developed in the future (e.g., fifth generation(5G), 6G, etc.). The baseband circuitry 904 (e.g., one or more ofbaseband processors 904 a-d) may handle various radio control functionsthat enable communication with one or more radio networks via the RFcircuitry 906. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 904 may include Fast-FourierTransform (FFT), precoding, and/or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 904 may include convolution, tail-biting convolution,turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 904 may include elements ofa protocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. A central processing unit (CPU) 904 e of thebaseband circuitry 904 may be configured to run elements of the protocolstack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. Insome embodiments, the baseband circuitry may include one or more audiodigital signal processor(s) (DSP) 904 f. The audio DSP(s) 904 f may beinclude elements for compression/decompression and echo cancellation andmay include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 904 and the application circuitry902 may be implemented together such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 904 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 904 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), a wireless personal area network(WPAN). Embodiments in which the baseband circuitry 904 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 906 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 906 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 906 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 908 and provide baseband signals to the baseband circuitry904. RF circuitry 906 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 904 and provide RF output signals to the FEMcircuitry 908 for transmission.

In some embodiments, the RF circuitry 906 may include a receive signalpath and a transmit signal path. The receive signal path of the RFcircuitry 906 may include mixer circuitry 906 a, amplifier circuitry 906b and filter circuitry 906 c. The transmit signal path of the RFcircuitry 906 may include filter circuitry 906 c and mixer circuitry 906a. RF circuitry 906 may also include synthesizer circuitry 906 d forsynthesizing a frequency for use by the mixer circuitry 906 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 906 a of the receive signal path may be configuredto down-convert RF signals received from the FEM circuitry 908 based onthe synthesized frequency provided by synthesizer circuitry 906 d. Theamplifier circuitry 906 b may be configured to amplify thedown-converted signals and the filter circuitry 906 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 904 for further processing. In some embodiments, the outputbaseband signals may be zero-frequency baseband signals, although thisis not a requirement. In some embodiments, mixer circuitry 906 a of thereceive signal path may comprise passive mixers, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 906 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 906 d togenerate RF output signals for the FEM circuitry 908. The basebandsignals may be provided by the baseband circuitry 904 and may befiltered by filter circuitry 906 c. The filter circuitry 906 c mayinclude a low-pass filter (LPF), although the scope of the embodimentsis not limited in this respect.

In some embodiments, the mixer circuitry 906 a of the receive signalpath and the mixer circuitry 906 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadrature downconversion and/or up conversion respectively. In some embodiments, themixer circuitry 906 a of the receive signal path and the mixer circuitry906 a of the transmit signal path may include two or more mixers and maybe arranged for image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 906 a of the receive signal path andthe mixer circuitry 906 a may be arranged for direct down conversionand/or direct up conversion, respectively. In some embodiments, themixer circuitry 906 a of the receive signal path and the mixer circuitry906 a of the transmit signal path may be configured for super-heterodyneoperation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 906 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry904 may include a digital baseband interface to communicate with the RFcircuitry 906.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 906 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 906 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 906 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 906 a of the RFcircuitry 906 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 906 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 904 orthe applications processor 902 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications processor 902.

Synthesizer circuitry 906 d of the RF circuitry 906 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 906 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 906 may include an IQ/polar converter.

FEM circuitry 908 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 910, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 906 for furtherprocessing. FEM circuitry 908 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 906 for transmission by one ormore of the one or more antennas 910.

In some embodiments, the FEM circuitry 908 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include a low-noiseamplifier (LNA) to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 906). Thetransmit signal path of the FEM circuitry 908 may include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 906), and one or more filters to generate RF signals forsubsequent transmission (e.g., by one or more of the one or moreantennas 910.

In some embodiments, the UE device 900 may include additional elementssuch as, for example, memory/storage, display, camera, sensor, and/orinput/output (I/O) interface.

FIG. 10 illustrates an embodiment of a communications device 1000 thatmay implement one or more of UE 102, eNB 106, MME 110, AS 202, corenetwork 108, server 128, message flows 200, 300, 320, 340, 360, logicflow 700, logic flow 720, storage medium 800, storage medium 850, and UE900. In various embodiments, device 1000 may comprise a logic circuit1028. The logic circuit 1028 may include physical circuits to performoperations described for one or more of UE 102, eNB 106, MME 110, AS202, core network 108, server 128, message flows 200, 300, 320, 340,360, logic flow 700, logic flow 720, storage medium 800, storage medium850, and UE 900, for example. As shown in FIG. 10, device 1000 mayinclude a radio interface 1010, baseband circuitry 1020, and computingplatform 1030, although the embodiments are not limited to thisconfiguration.

The device 1000 may implement some or all of the structure and/oroperations for one or more of UE 102, eNB 106, MME 110, AS 202, corenetwork 108, server 128, message flows 200, 300, 320, 340, 360, logicflow 700, logic flow 720, storage medium 800, storage medium 850, and UE900, and logic circuit 1028 in a single computing entity, such asentirely within a single device. Alternatively, the device 1000 maydistribute portions of the structure and/or operations for one or moreof UE 102, eNB 106, MME 110, AS 202, core network 108, server 128,message flows 200, 300, 320, 340, 360, logic flow 700, logic flow 720,storage medium 800, storage medium 850, and UE 900, and logic circuit1028 across multiple computing entities using a distributed systemarchitecture, such as a client-server architecture, a 3-tierarchitecture, an N-tier architecture, a tightly-coupled or clusteredarchitecture, a peer-to-peer architecture, a master-slave architecture,a shared database architecture, and other types of distributed systems.The embodiments are not limited in this context.

In one embodiment, radio interface 1010 may include a component orcombination of components adapted for transmitting and/or receivingsingle-carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK), orthogonal frequency divisionmultiplexing (OFDM), and/or single-carrier frequency division multipleaccess (SC-FDMA) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. Radiointerface 1010 may include, for example, a receiver 1012, a frequencysynthesizer 1014, and/or a transmitter 1016. Radio interface 1010 mayinclude bias controls, a crystal oscillator and/or one or more antennas1018-f. In another embodiment, radio interface 1010 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 1020 may communicate with radio interface 1010 toprocess receive and/or transmit signals and may include, for example, amixer for down-converting received RF signals, an analog-to-digitalconverter 1022 for converting analog signals to digital form, adigital-to-analog converter 1024 for converting digital signals toanalog form, and a mixer for up-converting signals for transmission.Further, baseband circuitry 1020 may include a baseband or physicallayer (PHY) processing circuit 1026 for PHY link layer processing ofrespective receive/transmit signals. Baseband circuitry 1020 mayinclude, for example, a medium access control (MAC) processing circuit1027 for MAC/data link layer processing. Baseband circuitry 1020 mayinclude a memory controller 1032 for communicating with MAC processingcircuit 1027 and/or a computing platform 1030, for example, via one ormore interfaces 1034.

In some embodiments, PHY processing circuit 1026 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames. Alternatively or in addition, MAC processingcircuit 1027 may share processing for certain of these functions orperform these processes independent of PHY processing circuit 1026. Insome embodiments, MAC and PHY processing may be integrated into a singlecircuit.

The computing platform 1030 may provide computing functionality for thedevice 1000. As shown, the computing platform 1030 may include aprocessing component 1040. In addition to, or alternatively of, thebaseband circuitry 1020, the device 1000 may execute processingoperations or logic for one or more of UE 102, eNB 106, MME 110, AS 202,core network 108, server 128, message flows 200, 300, 320, 340, 360,logic flow 700, logic flow 720, storage medium 800, storage medium 850,and UE 900, and logic circuit 1028 using the processing component 1040.The processing component 1040 (and/or PHY 1026 and/or MAC 1027) maycomprise various hardware elements, software elements, or a combinationof both. Examples of hardware elements may include devices, logicdevices, components, processors, microprocessors, circuits, processorcircuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), memoryunits, logic gates, registers, semiconductor device, chips, microchips,chip sets, and so forth. Examples of software elements may includesoftware components, programs, applications, computer programs,application programs, system programs, software development programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints, as desired for a given implementation.

The computing platform 1030 may further include other platformcomponents 1050. Other platform components 1050 include common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components (e.g., digital displays), powersupplies, and so forth. Examples of memory units may include withoutlimitation various types of computer readable and machine readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Device 1000 may be, for example, an ultra-mobile device, a mobiledevice, a fixed device, a machine-to-machine (M2M) device, a personaldigital assistant (PDA), a mobile computing device, a smart phone, atelephone, a digital telephone, a cellular telephone, user equipment,eBook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, display, television,digital television, set top box, wireless access point, base station,node B, subscriber station, mobile subscriber center, radio networkcontroller, router, hub, gateway, bridge, switch, machine, orcombination thereof. Accordingly, functions and/or specificconfigurations of device 1000 described herein, may be included oromitted in various embodiments of device 1000, as suitably desired.

Embodiments of device 1000 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1018-f) for transmissionand/or reception using adaptive antenna techniques for beamforming orspatial division multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of device 1000 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 1000 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 1000 shown in theblock diagram of FIG. 10 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

FIG. 11 illustrates an embodiment of a broadband wireless access system1100. As shown in FIG. 11, broadband wireless access system 1100 may bean internet protocol (IP) type network comprising an internet 1110 typenetwork or the like that is capable of supporting mobile wireless accessand/or fixed wireless access to internet 1110. In one or moreembodiments, broadband wireless access system 1100 may comprise any typeof orthogonal frequency division multiple access (OFDMA)-based orsingle-carrier frequency division multiple access (SC-FDMA)-basedwireless network, such as a system compliant with one or more of the3GPP LTE Specifications and/or IEEE 802.16 Standards, and the scope ofthe claimed subject matter is not limited in these respects.

In the exemplary broadband wireless access system 1100, radio accessnetworks (RANs) 1112 and 1118 are capable of coupling with evolved nodeBs (eNBs) 1114 and 1120, respectively, to provide wireless communicationbetween one or more fixed devices 1116 and internet 1110 and/or betweenor one or more mobile devices 1122 and Internet 1110. One example of afixed device 1116 and a mobile device 1122 is device 1000 of FIG. 10,with the fixed device 1116 comprising a stationary version of device1000 and the mobile device 1122 comprising a mobile version of device1000. RANs 1112 and 1118 may implement profiles that are capable ofdefining the mapping of network functions to one or more physicalentities on broadband wireless access system 1100. eNBs 1114 and 1120may comprise radio equipment to provide RF communication with fixeddevice 1116 and/or mobile device 1122, such as described with referenceto device 1000, and may comprise, for example, the PHY and MAC layerequipment in compliance with a 3GPP LTE Specification or an IEEE 802.16Standard. eNBs 1114 and 1120 may further comprise an IP backplane tocouple to Internet 1110 via RANs 1112 and 1118, respectively, althoughthe scope of the claimed subject matter is not limited in theserespects.

Broadband wireless access system 1100 may further comprise a visitedcore network (CN) 1124 and/or a home CN 1126, each of which may becapable of providing one or more network functions including but notlimited to proxy and/or relay type functions, for exampleauthentication, authorization and accounting (AAA) functions, dynamichost configuration protocol (DHCP) functions, or domain name servicecontrols or the like, domain gateways such as public switched telephonenetwork (PSTN) gateways or voice over internet protocol (VoIP) gateways,and/or internet protocol (IP) type server functions, or the like.However, these are merely example of the types of functions that arecapable of being provided by visited CN 1124 and/or home CN 1126, andthe scope of the claimed subject matter is not limited in theserespects. Visited CN 1124 may be referred to as a visited CN in the casewhere visited CN 1124 is not part of the regular service provider offixed device 1116 or mobile device 1122, for example where fixed device1116 or mobile device 1122 is roaming away from its respective home CN1126, or where broadband wireless access system 1100 is part of theregular service provider of fixed device 1116 or mobile device 1122 butwhere broadband wireless access system 1100 may be in another locationor state that is not the main or home location of fixed device 1116 ormobile device 1122. The embodiments are not limited in this context.

Fixed device 1116 may be located anywhere within range of one or both ofeNBs 1114 and 1120, such as in or near a home or business to providehome or business customer broadband access to Internet 1110 via eNBs1114 and 1120 and RANs 1112 and 1118, respectively, and home CN 1126. Itis worthy of note that although fixed device 1116 is generally disposedin a stationary location, it may be moved to different locations asneeded. Mobile device 1122 may be utilized at one or more locations ifmobile device 1122 is within range of one or both of eNBs 1114 and 1120,for example. In accordance with one or more embodiments, operationsupport system (OSS) 1128 may be part of broadband wireless accesssystem 1100 to provide management functions for broadband wirelessaccess system 1100 and to provide interfaces between functional entitiesof broadband wireless access system 1100. Broadband wireless accesssystem 1100 of FIG. 11 is merely one type of wireless network showing acertain number of the components of broadband wireless access system1100, and the scope of the claimed subject matter is not limited inthese respects.

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor. Some embodiments maybe implemented, for example, using a machine-readable medium or articlewhich may store an instruction or a set of instructions that, ifexecuted by a machine, may cause the machine to perform a method and/oroperations in accordance with the embodiments. Such a machine mayinclude, for example, any suitable processing platform, computingplatform, computing device, processing device, computing system,processing system, computer, processor, or the like, and may beimplemented using any suitable combination of hardware and/or software.The machine-readable medium or article may include, for example, anysuitable type of memory unit, memory device, memory article, memorymedium, storage device, storage article, storage medium and/or storageunit, for example, memory, removable or non-removable media, erasable ornon-erasable media, writeable or re-writeable media, digital or analogmedia, hard disk, floppy disk, Compact Disk Read Only Memory (CD-ROM),Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW),optical disk, magnetic media, magneto-optical media, removable memorycards or disks, various types of Digital Versatile Disk (DVD), a tape, acassette, or the like. The instructions may include any suitable type ofcode, such as source code, compiled code, interpreted code, executablecode, static code, dynamic code, encrypted code, and the like,implemented using any suitable high-level, low-level, object-oriented,visual, compiled and/or interpreted programming language.

The following examples pertain to further embodiments:

In a first example, an apparatus may comprise processing circuitry; andcomputer-readable storage media having stored thereon instructions forexecution by the processing circuitry to: determine, at user equipment(UE) operating in an Evolved Packet System (EPS) mobility management(EMM)-IDLE mode and configured to use EPS services with control planeCellular Internet of Things (CIoT) EPS optimization, to initiate aservice request procedure to enable a transfer of user data via acontrol plane; generate a service request message that contains aservice type information element (IE) comprising a service type valueset to indicate either a mobile originating request or a mobileterminating request; and send the service request message to a mobilitymanagement entity (MME) to initiate the service request procedure.

In the apparatus of any previous examples, the computer-readable storagemedia may have stored thereon instructions for execution by theprocessing circuitry to: identify user data to be sent to the MME; andinclude an EPS session management (ESM) data transport message in theservice request message, the ESM data transport message to comprise theuser data.

In the apparatus of any previous examples, the service request messagemay comprise an ESM message container information element (IE)containing the ESM data transport message.

In the apparatus of any previous examples, the computer-readable storagemedia of the second example may have stored thereon instructions forexecution by the processing circuitry to: determine to initiate theservice request procedure in response to a determination that uplinkuser data is pending at the UE; and set the service type value toindicate a mobile originating request.

In the apparatus of any previous examples, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to: determine to initiate the service request procedure inresponse to receipt of a paging message; and set the service type valueto indicate a mobile terminating request.

In the apparatus of any previous examples, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to determine that the service request procedure has beensuccessfully completed based on receipt of a security protectednon-access-stratum (NAS) message from the MME.

In the apparatus of any previous examples, the security protected NASmessage to comprise a service accept message.

In the apparatus of any previous examples, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to: identify one or more EPS bearer contexts that an EPSbearer context status information element (IE) comprised in the serviceaccept message indicates as being inactive; and locally deactivate theidentified one or more EPS bearer contexts.

In the apparatus of any previous examples, the security protected NASmessage to comprise a security mode command message or an EPS sessionmanagement (ESM) data transport message.

In the apparatus of any previous examples, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to cause the UE to enter an EMM-REGISTERED state in responseto a determination that the service request procedure has beensuccessfully completed.

In the apparatus of any previous examples, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to reset a service request attempt counter in response to adetermination that the service request procedure has been successfullycompleted.

In the apparatus of any previous examples, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to stop a timer T3417 in response to a determination that theservice request procedure has been successfully completed.

In the apparatus of any previous examples, comprising radio frequency(RF) circuitry to generate RF signals comprising the service requestmessage; and at least one antenna to transmit the RF signals.

In a second example, at least one computer-readable storage mediumcomprising a set of instructions that, in response to being executed atuser equipment (UE), cause the UE to: access a paging message receivedwhile the UE is in an Evolved Packet System (EPS) mobility management(EMM)-IDLE state and using EPS services with control plane CellularInternet of Things (CIoT) EPS optimization; determine, based on thepaging message, that a mobility management entity (MME) has user data tosend to the UE; and send a service request message to the MME toinitiate a service request procedure to enable the UE to receive theuser data via a control plane.

In the computer-readable storage medium of any previous examples,comprising determine, based on the paging message, that a mobilitymanagement entity (MME) has user data to send to the UE.

In the computer-readable storage medium of any previous examples, thepaging message to include a first parameter to indicate a source ofdownlink data, and a second parameter to indicate whether the controlplane or a data plane will transfer the user data.

In the computer-readable storage medium of any previous examples, theservice request message to contain a service type information element(IE) comprising a value indicating a mobile terminating request.

In the computer-readable storage medium of any previous examples,comprising instructions that, in response to being executed at the UE,cause the UE to: identify uplink user data pending at the UE; andinclude the uplink user data in the service request message.

In the computer-readable storage medium of any previous examples, theservice request message to comprise an EPS session management (ESM)message container information element (IE) containing an ESM datatransport message, the ESM data transport message to contain the uplinkuser data.

In the computer-readable storage medium of any previous examples,comprising instructions that, in response to being executed at the UE,cause the UE to determine that the service request procedure has beensuccessfully completed based receipt of a security protectednon-access-stratum (NAS) message from the MME.

In the computer-readable storage medium of any previous examples, thesecurity protected NAS message to comprise a service accept message.

In the computer-readable storage medium of any previous examples,comprising instructions that, in response to being executed at the UE,cause the UE to: identify one or more EPS bearer contexts that an EPSbearer context status information element (IE) comprised in the serviceaccept message indicates as being inactive; and locally deactivate theidentified one or more EPS bearer contexts.

In the computer-readable storage medium of any previous examples, thesecurity protected NAS message to comprise a security mode commandmessage or an EPS session management (ESM) data transport message.

In the computer-readable storage medium of any previous examples,comprising instructions that, in response to being executed at the UE,cause the UE to determine, based on the paging message, that the MMEwill send the user data via the control plane.

In the computer-readable storage medium of any previous examples, thepaging message to include a first parameter to indicate a source ofdownlink data, and a second parameter to indicate whether the controlplane or a data plane will transfer the user data.

In a third example, an apparatus, comprising: processing circuitry; andcomputer-readable storage media having stored thereon instructions forexecution by the processing circuitry to: access, at a mobilitymanagement entity (MME), a service request message received from userequipment (UE), the service request message to contain a service typeinformation element (IE); identify a service type value comprised in theservice type IE; and in response to a determination that the servicetype value indicates a mobile terminating request, initiate a transportof user data to the UE via a control plane.

In an apparatus of any previous example, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to send an EPS session management (ESM) data transport messageto the UE, the ESM data transport message to contain the user data.

In an apparatus of any previous example, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to: detect a presence of an EPS session management (ESM)message container IE within the service request message; and forwardcontents of the ESM message container IE.

In an apparatus of any previous example, the contents of the ESM messagecontainer IE to comprise an ESM data transport message containing userdata originating from the UE.

In a fourth example, a method, comprising: accessing a paging messagereceived while the UE is in an Evolved Packet System (EPS) mobilitymanagement (EMM)-IDLE state and using EPS services with control planeCellular Internet of Things (CIoT) EPS optimization; determining, basedon the paging message, that a mobility management entity (MME) has userdata to send to the UE; and sending a service request message to the MMEto initiate a service request procedure to enable the UE to receive theuser data via a control plane.

In the method of any previous example, comprising determining, based onthe paging message, that a mobility management entity (MME) has userdata to send to the UE.

In the method of any previous examples, the paging message to include afirst parameter to indicate a source of downlink data, and a secondparameter to indicate whether the control plane or a data plane willtransfer the user data.

In the method of any previous example, the service request message tocontain a service type information element (IE) comprising a valueindicating a mobile terminating request.

In the method of any previous example, comprising identifying uplinkuser data pending at the UE; and including the uplink user data in theservice request message.

In the method of any previous example, the service request message tocomprise an EPS session management (ESM) message container informationelement (IE) containing an ESM data transport message, the ESM datatransport message to contain the uplink user data.

In the method of any previous example, comprising determining that theservice request procedure has been successfully completed based receiptof a security protected non-access-stratum (NAS) message from the MME.

In the method of any previous example, the security protected NASmessage to comprise a service accept message.

In the method of any previous example, comprising: identifying one ormore EPS bearer contexts that an EPS bearer context status informationelement (IE) comprised in the service accept message indicates as beinginactive; and locally deactivating the identified one or more EPS bearercontexts.

In the method of any previous example, the security protected NASmessage to comprise a security mode command message or an EPS sessionmanagement (ESM) data transport message.

In a fifth example, at least one computer-readable storage mediumcomprising a set of instructions that, in response to being executed ata processor, cause the processor to: access, at a mobility managemententity (MME), a service request message received from user equipment(UE), the service request message to contain a service type informationelement (IE); identify a service type value comprised in the servicetype IE; and in response to a determination that the service type valueindicates a mobile terminating request, initiate a transport of userdata to the UE via a control plane.

In the computer-readable storage medium of any previous example,comprising instructions that when executed cause the processor to sendan EPS session management (ESM) data transport message to the UE, theESM data transport message to contain the user data.

In the computer-readable storage medium of any previous example,comprising instructions that when executed cause the processor to:detect a presence of an EPS session management (ESM) message containerIE within the service request message; and forward contents of the ESMmessage container IE.

In the computer-readable storage medium of any previous example, thecontents of the ESM message container IE to comprise an ESM datatransport message containing user data originating from the UE.

In a sixth example, a method, comprising: accessing, at a mobilitymanagement entity (MME), a service request message received from userequipment (UE), the service request message to contain a service typeinformation element (IE); identifying a service type value comprised inthe service type IE; and in response to a determination that the servicetype value indicates a mobile terminating request, initiating atransport of user data to the UE via a control plane.

In the method of any previous example, comprising sending an EPS sessionmanagement (ESM) data transport message to the UE, the ESM datatransport message to contain the user data.

In the method of any previous example, comprising: detecting a presenceof an EPS session management (ESM) message container IE within theservice request message; and forwarding contents of the ESM messagecontainer IE.

In the method of any previous example, the contents of the ESM messagecontainer IE to comprise an ESM data transport message containing userdata originating from the UE.

In a seventh example, a system, comprising: a UE according to any of theprevious examples; a memory controller; and a display.

In an eighth example, a system, comprising: an apparatus according toany of the previous examples; a memory controller; and a display.

In a ninth example, an apparatus, comprising: means for determining, atuser equipment (UE) operating in an Evolved Packet System (EPS) mobilitymanagement (EMM)-IDLE mode and configured to use EPS services withcontrol plane Cellular Internet of Things (CIoT) EPS optimization, toinitiate a service request procedure to enable a transfer of user datavia a control plane; means for generating a service request message thatcontains a service type information element (IE) comprising a servicetype value set to indicate either a mobile originating request or amobile terminating request; and means for sending the service requestmessage to a mobility management entity (MME) to initiate the servicerequest procedure.

In the apparatus of any previous example, comprising: means foridentifying user data to be sent to the MME; and means for including anEPS session management (ESM) data transport message in the servicerequest message, the ESM data transport message to comprise the userdata.

In the apparatus of any previous example, the service request message tocomprise an ESM message container information element (IE) containingthe ESM data transport message.

In the apparatus of any previous example, the apparatus of claim 45,comprising: means for determining to initiate the service requestprocedure in response to a determination that uplink user data ispending at the UE; and means for setting the service type value toindicate a mobile originating request.

In the apparatus of any previous example, comprising: means fordetermining to initiate the service request procedure in response toreceipt of a paging message; and means for setting the service typevalue to indicate a mobile terminating request.

In the apparatus of any previous example, comprising means fordetermining that the service request procedure has been successfullycompleted based on receipt of a security protected non-access-stratum(NAS) message from the MME.

In the apparatus of any previous example, the security protected NASmessage to comprise a service accept message.

In the apparatus of any previous example, comprising: means foridentifying one or more EPS bearer contexts that an EPS bearer contextstatus information element (IE) comprised in the service accept messageindicates as being inactive; and means for locally deactivating theidentified one or more EPS bearer contexts.

In the apparatus of any previous example, the security protected NASmessage to comprise a security mode command message or an EPS sessionmanagement (ESM) data transport message.

In the apparatus of any previous example, comprising means for enteringan EMM-REGISTERED state in response to a determination that the servicerequest procedure has been successfully completed.

In the apparatus of any previous example, comprising means for resettinga service request attempt counter in response to a determination thatthe service request procedure has been successfully completed.

In the apparatus of any previous example, comprising means for stoppinga timer T3417 in response to a determination that the service requestprocedure has been successfully completed.

In the apparatus of any previous example, comprising: means forgenerating radio-frequency (RF) signals comprising the service requestmessage; and means for transmitting the RF signals.

In a tenth example, an apparatus, comprising: means for accessing, at amobility management entity (MME), a service request message receivedfrom user equipment (UE), the service request message to contain aservice type information element (IE); means for identifying a servicetype value comprised in the service type IE; and in response to adetermination that the service type value indicates a mobile terminatingrequest, means for initiating a transport of user data to the UE via acontrol plane.

In the apparatus of any previous example, comprising means for sendingan EPS session management (ESM) data transport message to the UE, theESM data transport message to contain the user data.

In the apparatus of any previous example, comprising: means fordetecting a presence of an EPS session management (ESM) messagecontainer IE within the service request message; and means forforwarding contents of the ESM message container IE.

In the apparatus of any previous example, the contents of the ESMmessage container IE to comprise an ESM data transport messagecontaining user data originating from the UE.

In the apparatus of any previous example, comprising: means forgenerating radio-frequency (RF) signals comprising the service requestmessage; and means for transmitting the RF signals.

In an eleventh example, a user equipment (UE), comprising: processingcircuitry; and computer-readable storage media having stored thereoninstructions for execution by the processing circuitry to: access apaging message received while the UE is in an Evolved Packet System(EPS) mobility management (EMM)-IDLE state and using EPS services withcontrol plane Cellular Internet of Things (CIoT) EPS optimization;determine, based on the paging message, that a mobility managemententity (MME) has user data to send to the UE; and send a service requestmessage to the MME to initiate a service request procedure to enable theUE to receive the user data via a control plane.

In the UE of any previous example, the service request message tocontain a service type information element (IE) comprising a valueindicating a mobile terminating request.

In the UE of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to: identify uplinkuser data pending at the UE; and include the uplink user data in theservice request message.

In the UE of any previous example, the service request message tocomprise an EPS session management (ESM) message container informationelement (IE) containing an ESM data transport message, the ESM datatransport message to contain the uplink user data.

In the UE of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to determine that theservice request procedure has been successfully completed based receiptof a security protected non-access-stratum (NAS) message from the MME.

In the UE of any previous example, the security protected NAS message tocomprise a service accept message.

In the UE of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to: identify one ormore EPS bearer contexts that an EPS bearer context status informationelement (IE) comprised in the service accept message indicates as beinginactive; and locally deactivate the identified one or more EPS bearercontexts.

In the UE of any previous example, the security protected NAS message tocomprise a security mode command message or an EPS session management(ESM) data transport message.

In the UE of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to determine, basedon the paging message, that the MME will send the user data via thecontrol plane.

In the UE of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to the paging messageto include a first parameter to indicate a source of downlink data, anda second parameter to indicate whether the control plane or a data planewill transfer the user data.

In a twelfth example, a method, comprising: accessing a paging messagereceived while the UE is in an Evolved Packet System (EPS) mobilitymanagement (EMM)-IDLE state and using EPS services with control planeCellular Internet of Things (CIoT) EPS optimization; determining, basedon the paging message, that a mobility management entity (MME) has userdata to send to the UE; and sending a service request message to the MMEto initiate a service request procedure to enable the UE to receive theuser data via a control plane.

In the method of any previous example, the service request message tocontain a service type information element (IE) comprising a valueindicating a mobile terminating request.

In the method of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to: identify uplinkuser data pending at the UE; and include the uplink user data in theservice request message.

In the method of any previous example, the service request message tocomprise an EPS session management (ESM) message container informationelement (IE) containing an ESM data transport message, the ESM datatransport message to contain the uplink user data.

In the method of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to determine that theservice request procedure has been successfully completed based receiptof a security protected non-access-stratum (NAS) message from the MME.

In the method of any previous example, the security protected NASmessage to comprise a service accept message.

In the method of any previous example, comprising instructions that, inresponse to being executed at the UE, cause the UE to: identify one ormore EPS bearer contexts that an EPS bearer context status informationelement (IE) comprised in the service accept message indicates as beinginactive; and locally deactivate the identified one or more EPS bearercontexts.

In the method of any previous example, the security protected NASmessage to comprise a security mode command message or an EPS sessionmanagement (ESM) data transport message.

In the method of any previous example, comprising determining, based onthe paging message, that the MME will send the user data via the controlplane.

In the method of any previous example, the paging message to include afirst parameter to indicate a source of downlink data, and a secondparameter to indicate whether the control plane or a data plane willtransfer the user data.

Numerous specific details have been set forth herein to provide athorough understanding of the embodiments. It will be understood bythose skilled in the art, however, that the embodiments may be practicedwithout these specific details. In other instances, well-knownoperations, components, and circuits have not been described in detailso as not to obscure the embodiments. It can be appreciated that thespecific structural and functional details disclosed herein may berepresentative and do not necessarily limit the scope of theembodiments.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are not intendedas synonyms for each other. For example, some embodiments may bedescribed using the terms “connected” and/or “coupled” to indicate thattwo or more elements are in direct physical or electrical contact witheach other. The term “coupled,” however, may also mean that two or moreelements are not in direct contact with each other, but yet stillco-operate or interact with each other.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

It should be noted that the methods described herein do not have to beexecuted in the order described, or in any particular order. Moreover,various activities described with respect to the methods identifiedherein can be executed in serial or parallel fashion.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. It is to be understood that the abovedescription has been made in an illustrative fashion, and not arestrictive one. Combinations of the above embodiments, and otherembodiments not specifically described herein will be apparent to thoseof skill in the art upon reviewing the above description. Thus, thescope of various embodiments includes any other applications in whichthe above compositions, structures, and methods are used.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. § 1.72(b), requiring an abstract that will allowthe reader to quickly ascertain the nature of the technical disclosure.It is submitted with the understanding that it will not be used tointerpret or limit the scope or meaning of the claims. In addition, inthe foregoing Detailed Description, it can be seen that various featuresare grouped together in a single embodiment for the purpose ofstreamlining the disclosure. This method of disclosure is not to beinterpreted as reflecting an intention that the claimed embodimentsrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter lies in lessthan all features of a single disclosed embodiment. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate preferred embodiment. In theappended claims, the terms “including” and “in which” are used as theplain-English equivalents of the respective terms “comprising” and“wherein,” respectively. Moreover, the terms “first,” “second,” and“third,” etc. are used merely as labels, and are not intended to imposenumerical requirements on their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. An apparatus, comprising: processing circuitry;and a non-transitory computer-readable storage media having storedthereon instructions for execution by the processing circuitry to:determine, at user equipment (UE) operating in an Evolved Packet System(EPS) mobility management (EMM)-IDLE mode and configured to use EPSservices with control plane Cellular Internet of Things (CIoT) EPSoptimization, to initiate a service request procedure to enable atransfer of user data via a control plane; generate a service requestmessage that contains a service type information element (IE) comprisinga service type value set to indicate a mobile terminating request;identify user data to be sent to a mobility management entity (MME);include an EPS session management (ESM) data transport message in theservice request message, the ESM data transport message to comprise theuser data; and send the service request message to the MME to initiatethe service request procedure.
 2. The apparatus of claim 1, the servicerequest message to comprise an ESM message container information element(IE) containing the ESM data transport message.
 3. The apparatus ofclaim 1, the computer-readable storage media having stored thereoninstructions for execution by the processing circuitry to: determine toinitiate the service request procedure in response to receipt of apaging message; and set the service type value to indicate the mobileterminating request.
 4. The apparatus of claim 1, the computer-readablestorage media having stored thereon instructions for execution by theprocessing circuitry to determine that the service request procedure hasbeen successfully completed based on receipt of a security protectednon-access-stratum (NAS) message from the MME.
 5. The apparatus of claim4, the security protected NAS message to comprise a service acceptmessage.
 6. The apparatus of claim 5, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to: identify one or more EPS bearer contexts that an EPSbearer context status information element (IE) comprised in the serviceaccept message indicates as being inactive; and locally deactivate theidentified one or more EPS bearer contexts.
 7. The apparatus of claim 4,the security protected NAS message to comprise a security mode commandmessage or an EPS session management (ESM) data transport message. 8.The apparatus of claim 1, the computer-readable storage media havingstored thereon instructions for execution by the processing circuitry tocause the UE to enter an EMM-REGISTERED state in response to adetermination that the service request procedure has been successfullycompleted.
 9. The apparatus of claim 1, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to reset a service request attempt counter in response to adetermination that the service request procedure has been successfullycompleted.
 10. The apparatus of claim 1, the computer-readable storagemedia having stored thereon instructions for execution by the processingcircuitry to stop a timer T3417 in response to a determination that theservice request procedure has been successfully completed.
 11. Theapparatus of claim 1, comprising: radio frequency (RF) circuitry togenerate RF signals comprising the service request message; and at leastone antenna to transmit the RF signals.
 12. At least one non-transitorycomputer-readable storage medium comprising a set of instructions that,in response to being executed at user equipment (UE), cause the UE to:access a paging message received while the UE is in an Evolved PacketSystem (EPS) mobility management (EMM)-IDLE state and using EPS serviceswith control plane Cellular Internet of Things (CIoT) EPS optimization;determine, based on the paging message, that a mobility managemententity (MME) has user data to send to the UE; determine, based on thepaging message, that the MME will send the user data via a controlplane; send a service request message to the MME to initiate a servicerequest procedure to enable the UE to receive the user data via thecontrol plane, the service request message to contain a service typeinformation element (IE) comprising a value indicating a mobileterminating request; and receive an EPS session management (ESM) datatransport message from the MME, the ESM data transport message tocontain the user data.
 13. The at least one computer-readable storagemedium of claim 12, comprising instructions that, in response to beingexecuted at the UE, cause the UE to: identify uplink user data pendingat the UE; and include the uplink user data in the service requestmessage.
 14. The at least one computer-readable storage medium of claim13, the service request message to further comprise an EPS sessionmanagement (ESM) message container information element (IE) containingan ESM data transport message, the ESM data transport message to containthe uplink user data.
 15. The at least one computer-readable storagemedium of claim 12, comprising instructions that, in response to beingexecuted at the UE, cause the UE to determine that the service requestprocedure has been successfully completed based on receipt of a securityprotected non-access-stratum (NAS) message from the MME.
 16. The atleast one computer-readable storage medium of claim 15, the securityprotected NAS message to comprise a service accept message.
 17. The atleast one computer-readable storage medium of claim 16, comprisinginstructions that, in response to being executed at the UE, cause the UEto: identify one or more EPS bearer contexts that an EPS bearer contextstatus information element (IE) comprised in the service accept messageindicates as being inactive; and locally deactivate the identified oneor more EPS bearer contexts.
 18. The at least one computer-readablestorage medium of claim 15, the security protected NAS message tocomprise a security mode command message or an EPS session management(ESM) data transport message.
 19. An apparatus, comprising: processingcircuitry; and a non-transitory computer-readable storage media havingstored thereon instructions for execution by the processing circuitryto: access, at a mobility management entity (MME), a service requestmessage received from user equipment (UE), the service request messageto contain a service type information element (IE); identify a servicetype value comprised in the service type IE; in response to adetermination that the service type value indicates a mobile terminatingrequest, initiate a transport of user data to the UE via a controlplane; and send an EPS session management (ESM) data transport messageto the UE, the ESM data transport message to contain the user data. 20.The apparatus of claim 19, the computer-readable storage media havingstored thereon instructions for execution by the processing circuitryto: detect a presence of an EPS session management (ESM) messagecontainer IE within the service request message; and forward contents ofthe ESM message container IE.
 21. The apparatus of claim 20, thecontents of the ESM message container IE to comprise an ESM datatransport message containing user data originating from the UE.